fix: correct booker email input #21077
Conversation
dosubot
bot
added
the
booking-page
| if (!props) { | ||
| return <div />; | ||
| } | ||
| return <Widgets.TextWidget type="email" id={props.name} noLabel={true} {...props} />; |
There was a problem hiding this comment.
We use input field in the rest of this components file - not sure why we used widget here.
|
It affects both Routing Form field and Booker field right? |
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (05/02/25)1 reviewer was added to this PR based on Keith Williams's automation. "Add ready-for-e2e label" took an action on this PR • (05/02/25)1 label was added to this PR based on Keith Williams's automation. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
mrge reviewed 1 file and found no issues. Review this PR in mrge.io.
Yes but the one thats rendered in the form not the form builder that uses a different set of components cal.com/packages/app-store/routing-forms/components/react-awesome-query-builder/widgets.tsx The RAQB form builder uses these components where as the components rendered in booker/forms use the components in cal.com/packages/features/form-builder/Components.tsx |
E2E results are ready! |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
Co-authored-by: Udit Takkar <[email protected]>
What does this PR do?
Uses the correct component in booker instead of the routing forms widgets
Summary by mrge
Fixed the booker email input to use the correct input component instead of the routing form widget. This ensures proper handling of email values in the form.